package rim;

import java.util.ArrayList;
import java.util.List;

import javax.annotation.Generated;
import javax.persistence.Embedded;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.JoinColumn;
import javax.persistence.ManyToOne;

import datatypes.r2.basic.CD;
import datatypes.r2.basic.CS;
import datatypes.r2.basic.ED;
import datatypes.r2.basic.II;
import datatypes.r2.basic.impl.CodedSimpleValue;
import datatypes.r2.basic.impl.ConceptDescriptor;
import datatypes.r2.basic.impl.EncapsulatedData;
import datatypes.r2.collectionsofquantities.IVL;
import datatypes.r2.collectionsofquantities.QSET;
import datatypes.r2.flavors.INT_NONNEG;
import datatypes.r2.flavors.ST_SIMPLE;
import datatypes.r2.flavors.impl.StringSimple;
import datatypes.r2.foundation.BL;
import datatypes.r2.foundation.DSET;
import datatypes.r2.quantities.TS;

/**
 * 
 * 
 * A record of something that is being done, has been done, can be done, or is
 * intended or requested to be done.
 * 
 * 已经做了一个纪录，正在做的事情，可以做，或有意或要求进行。
 * 
 * 
 * Acts connect to Entities in their Roles through Participations, and they
 * connect to other Acts through ActRelationships. Participations indicate the
 * performers, authors, and other responsible parties as well as subjects and
 * beneficiaries (including tools and material used in the performance of the
 * act, which are also subjects). The moodCode distinguishes among Acts that are
 * meant as factual records, records of intended or ordered services, and other
 * modalities in which acts can be recorded.
 * 
 * 行为连接到自己的角色，通过参股的实体，它们连接通过ActRelationships以其他行为。参与表示演员，作家，以及其他负责各方主体和受益者（
 * 包括工具和材料中的行为表现，这也是科）。该moodCode区别意味着，作为事实的记录，记录，有意或订购服务，并在其中的行为，可以记录的其他方式的行为中。
 * 
 * 
 * Acts are the pivot of the RIM: domain information and process records are
 * represented primarily in Acts. Any profession or business, including
 * healthcare, is primarily constituted of intentional and occasionally
 * non-intentional actions, performed and recorded by responsible actors. An
 * Act-instance is a record of such an action.
 * 
 * An Act-instance represents a "statement," according to Rector and Nowlan
 * (1991) [Foundations for an electronic medical record. Methods Inf Med. 30.]
 * 
 * An activity in the real world may progress from definition, through planning
 * and ordering to execution: these stages are represented as the moods of the
 * Act. Even though one might think of a single activity as progressing through
 * these stages, the "attributable statement" model of Act entails that this
 * progression be reflected by multiple Act-instances, each having one and only
 * one mood, and that this mood not change during the Act-instance's life cycle.
 * This is because the attribution and content of speech acts along this
 * progression of an activity may be different, and it is critical that a
 * permanent and faithful record be maintained of this progression. The
 * specification of orders or promises or plans must not be overwritten by the
 * specification of what was actually done, so as to allow recipients of the
 * information to compare actions with their earlier specifications.
 * Act-instances that describe this progression of the same real world activity
 * are linked through the ActRelationships (of the relationship category
 * "sequel").
 * 
 * Acts as statements are the only representations of real world facts or
 * processes in the HL7 RIM. The truth about the real world is constructed
 * through the combination (and arbitration) of such attributed statements only,
 * and there is no class in the RIM whose objects represent
 * "objective state of affairs" or "real processes" independent from attributed
 * statements. A factual statement may be made about recent (but past)
 * activities, authored (and signed) by the performer of such activities, e.g. a
 * surgical procedure report, clinic note, etc. Similarly, a status update may
 * be made about an activity that is presently in progress, authored by the
 * performer (or a close observer), and later superseded by a full procedure
 * report. Both status update and procedure report are acts, distinguished by
 * mood and state (see Act.statusCode) and completeness of information: neither
 * has any epistemological priority over the other except as judged by the
 * recipient of the information.
 * 
 * 行为是RIM的支点：主要是在行为表示域的信息和过程记录。任何专业或业务，包括医疗保健，主要是构成故意偶尔非蓄意的行动，执行和记录由负责演员。一项法令，
 * 实例​​是这样的行动的纪录。
 * 
 * 一项法令，例如“声明”，根据校长和Nowlan（1991）电子病历的基础。方法INF MED。 30。
 * 
 * 在现实世界中的活动可能会进步，从定义，通过规划和订购执行这些阶段的代表作为该法的情绪。即使有人可能会认为一个单一的活动，通过这些阶段的进展，带来的“
 * 归属声明
 * ”法模型，这种进展反映多个法的情况下，每一个和只有一个心情，这种情绪在不改变法实例的生命周期。这是因为沿着这一项活动的进展言语行为的归属和内容可能不同
 * ，这是至关重要的一个永久和忠实地记录保持这一进展。规范订单或承诺或计划必须是由什么实际完成的规范覆盖，以便让收件人的信息与他们早先的规范行动。
 * 法实例说明这同现实世界活动的进展挂钩通过的ActRelationships关系类“的续集”。
 * 
 * 作为报表的行为是现实世界中的事实或过程中的HL7
 * RIM的唯一交涉。关于现实世界的真相是通过这种归因语句只组合（仲裁）建造的，并没有在RIM的类，其对象表示
 * “客观事态”或“真正的过程”独立归因报表。关于最近的活动
 * （但过去），创作（签署）表演等活动，如一个事实的陈述可手术报告，诊所注意，等，同样，状态更新可能会作出有关的活动
 * ，目前正在进行创作，表演（或接近观察员），以及后来由一个完整的程序报告取代
 * 。状态更新和程序报告的行为，情绪和状态（见Act.statusCode）和资料的完整性区别，也没有任何认识论的优先级比其他除由信息接收者的判断。
 * 
 * 
 * Examples:
 * 
 * The kinds of acts that are common in health care include (1) clinical
 * observations, (2) assessments of health condition (such as problems and
 * diagnoses), (3) healthcare goals, (4) treatment services (such as medication,
 * surgery, physical and psychological therapy), (5) acts of assisting,
 * monitoring or attending, (6) training and education services to patients and
 * their next of kin, (7) notary services (such as advanced directives or living
 * will), (8) editing and maintaining documents, and many others.
 * 
 * 例子：
 * 
 * 保健中常见的行为，种类包括：（1）临床观察，（2）健康状况的评估（如问题和诊断），（3）医疗保健的目标，（4）处理服务（如药物治疗，手术，身体和心理治疗）
 * ，（5）行为（6）培训和教育服务，为病人和他们的近亲，（7）协助，监督或参加，公证服务（如先进的指令或生活），（8）编辑和维护文件，以及其他许多。
 * 
 * @author Obama
 * 
 */
@javax.persistence.Entity
public class Act extends InfrastructureRoot {
	/**
	 * 
	 */
	private static final long serialVersionUID = 1L;
	@Id
	@GeneratedValue(strategy = GenerationType.AUTO)
	private long actId;

	/**
	 * 
	 * Definition:
	 * 
	 * The major class of Acts to which an Act-instance belongs.
	 * 
	 * 一项法令，实例所属的行为的主要类。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * For Act-instances that have an Act.code, the Act.code SHALL be a
	 * specialization of the Act.classCode. The Act.code, however, cannot alter
	 * the meaning of the Act.classCode.
	 * 
	 * This attribute provides a tightly controlled vocabulary of Act class
	 * "types" that is balloted with the RIM, and can be used to represent a
	 * type enumeration that might have been represented as a physical class in
	 * the RIM, but was not because while it had unique meaning, it did not
	 * require unique attributes or unique patterns of associations. The "code"
	 * attribute defines a specific sub-type of this Act type, and is intended
	 * to allow use of rich terminologies such as LOINC and SNOMED to represent
	 * these sub-types.
	 * 
	 * 法“的实例，有一个Act.code，Act.code应是一个专业化的Act.classCode。然而，Act.code，不能改变的Act.
	 * classCode的意义。
	 * 
	 * 此属性提供了一个法类“类型”，即抽签与RIM，可以用来表示可能已作为在RIM的体育课代表的一个类型枚举严格控制的词汇，
	 * 但不是因为虽然它具有独特的也就是说，它并不需要独特属性或协会的独特模式。
	 * “代码”属性定义特定本法类型的子类型，是为了让丰富的用语，如LOINC的使用和SNOMED代表这些子类型。
	 * 
	 * 
	 * FormalConstraint:
	 * 
	 * Every Act-instance SHALL have a classCode. If the act class is not
	 * further specified, the most general Act.classCode (ACT) is used.
	 * 
	 * 每一个行为，实例应有classCode，。如果没有进一步明确的行为类，最的一般Act.classCode（ACT）的使用。
	 */
	@ManyToOne
	@JoinColumn(name = "classCode_id")
	private CodedSimpleValue classCode;

	/**
	 * Definition:
	 * 
	 * The intended use of the Act statement: as a report of fact, a command, a
	 * possibility, a goal, etc.
	 * 
	 * 该法案声明使用用途：作为事实上的报告，一个命令，一个可能性，一个目标，等
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * To describe the progression of a business activity from definition to
	 * planning to execution, etc., one must instantiate Act-instances in each
	 * of the required moods and link them using ActRelationship of general type
	 * "sequel." (See ActRelationship.typeCode.)
	 * 
	 * Since the mood code is a determining factor for the meaning of an entire
	 * Act object, the mood must always be known. This means that whenever an
	 * act object is instantiated, the mood attribute SHALL be assigned to a
	 * valid code, and the mood assignment SHALL NOT change throughout the
	 * lifetime of the act object.
	 * 
	 * The Act.moodCode modifies the meaning of the Act class in a controlled
	 * way, just as in natural language, grammatical form of a verb modifies the
	 * meaning of a sentence in defined ways. For example, if the mood is
	 * factual (event), then the entire act object represents a known fact. If
	 * the mood expresses a plan (intent), the entire act object represents the
	 * expectation of what should be done.
	 * 
	 * As the meaning of an Act-instance is factored in the mood code, the mood
	 * code affects the interpretation of the entire Act object and with it
	 * every property (attributes and associations). Note that the mood code
	 * affects the interpretation of the act object, and the meaning of the act
	 * object in turn determines the meaning of the attributes. However, the
	 * mood code does not arbitrarily change the meaning of individual
	 * attributes.
	 * 
	 * Acts have two kinds of act properties, inert and descriptive. Inert
	 * properties are not affected by the mood, but descriptive properties
	 * follow the mood of the object. For example, there is an identifier
	 * attribute Act.id, which gives a unique identification to an act object.
	 * Being a unique identifier for the object is in no way dependent on the
	 * mood of the act object. Therefore, the "interpretation" of the Act.id
	 * attribute is inert with respect to the act object's mood.
	 * 
	 * By contrast, most of the Act class attributes describe what the Act
	 * statement expresses. Descriptive properties of the Act class answer the
	 * questions who, whom, where, with what, how and when the action is done.
	 * The questions who, whom, with what, and where are answered by
	 * Participations, while how and when are answered by descriptive attributes
	 * and ActRelationships. The interpretation of a descriptive attribute is
	 * aligned with the interpretation of the entire act object, and controlled
	 * by the mood.
	 * 
	 * 描述自定义计划执行业务活动的进展等，必须实例化在每个所需的情绪法实例和它们连接使用普通型ActRelationship“续集。”
	 * （见ActRelationship.typeCode。）
	 * 
	 * 由于心情代码为整个法对象的含义是决定性的因素，心情必须始终闻名。这意味着，行为对象被实例化时，心情属性应被分配到一个有效的代码，和情绪转让，
	 * 不得改变整个一生的行为对象。
	 * 
	 * Act.moodCode修改在受控法类的含义，就像在自然语言，动词的语法形式修改在定义方法的句子的含义。例如，如果是事实（事件）的心情，
	 * 那么整个的行为对象代表一个众所周知的事实。如果心情表示计划（意向），整个行为对象的代表应该怎样做的期望。
	 * 
	 * 作为一项法令，实例​​的含义是在情绪代码的因素，心情的代码影响了整个法对象和它的每个属性的解释（属性和关联）。注意情绪代码影响的行为对象的解释，
	 * 并反过来的行为对象的含义决定了属性的含义。然而，心情代码不随意改变个别属性的含义。
	 * 
	 * 行为有两种行为的性质，惰性和描述。惰性属性的心情没有受到影响，但描述的属性按照对象的情绪。例如，有一个的标识符属性Act.id的，
	 * 给人以独特的标识的行为对象。作为一个对象的唯一标识符，是没有办法依赖于行为对象的情绪。因此，“解释”的Act.id属性是惰性与尊重行为对象的心情。
	 * 
	 * 相比之下，大多数法类属性描述法“声明表示。该法类的描述属性回答的问题，谁，谁，在哪里，什么，何时以及如何完成的动作。的问题，谁，谁，什么，
	 * 并回答参与，而如何时，以描述性属性和ActRelationships的回答。一个描述属性的解释是一致的整个行为对象的解释，情绪控制。
	 * 
	 * 
	 * Examples:
	 * 
	 * To illustrate the effect of mood code, consider a "blood glucose"
	 * observation.
	 * 
	 * The Definition mood specifies the Act of "obtaining blood glucose."
	 * Participations describe in general the characteristics of the people who
	 * must be involved in the act, and the required objects, e.g., specimen,
	 * facility, equipment, etc. involved. The Observation.value specifies the
	 * absolute domain (range) of the observation (e.g., 15-500 mg/dl).
	 * 
	 * In Intent mood the author of the intent expresses the intent that he or
	 * someone else "should obtain blood glucose." The participations are the
	 * people actually or supposedly involved in the intended act, especially
	 * the author of the intent or any individual assignments for group intents,
	 * and the objects actually or supposedly involved in the act (e.g.,
	 * specimen sent, equipment requirements, etc.). The Observation.value is
	 * usually not specified, since the intent is to measure blood glucose, not
	 * to measure blood glucose in a specific range. (But compare with GOAL
	 * below).
	 * 
	 * In Request mood, a kind of intent, the author requests
	 * "please measure blood glucose." The Participations identify the people
	 * actually and supposedly involved in the act, especially the order placer
	 * and the designated filler, and the objects actually or supposedly
	 * involved in the act (e.g., specimen sent, equipment requirements, etc.).
	 * The Observation.value is usually not specified, since the order is not to
	 * measure blood glucose in a specific range.
	 * 
	 * In Event mood, the author states that "blood glucose was measured."
	 * Participations indicate the people actually involved in the act, and the
	 * objects actually involved (e.g., specimen, facilities, equipment). The
	 * Observation.value is the value actually obtained (e.g., 80 mg/dL, or <15
	 * mg/dL).
	 * 
	 * In Event Criterion (not to be confused with Criterion) mood, an author
	 * considers a certain class of "obtaining blood glucose" possibly with a
	 * certain value (range) as outcome. The Participations constrain the
	 * criterion, for instance, to a particular patient. The Observation.value
	 * is the range in which the criterion would hold (e.g. > 180 mg/dL or
	 * 200-300 mg/dL).
	 * 
	 * In Goal mood (a kind of criterion), the author states that
	 * "our goal is to be able to obtain blood glucose with the given value (range)."
	 * The Participations are similar to those in Intent mood, especially the
	 * author of the goal and the patient for whom the goal is made. The
	 * Observation.value is the range which defines when the goal is met (e.g.
	 * 80-120 mg/dl).
	 * 
	 * 为了说明心情代码的效果，考虑“血糖”观察。
	 * 
	 * 定义情绪指定法“取得的血糖。”参与一般的描述，参与的人必须在参与的行为，以及所需的对象，例如，标本，设施，设备等的特点。
	 * Observation.value指定观察绝对域（范围）（例如，15-500毫克/分升）。
	 * 
	 * 作者的意图，在意向书的心情表示，他或其他​​人“应该获得血糖的意图。”参与是预期的行为所涉及的实际或假想的人，
	 * 尤其是作者的意图或任何个人作业组的意图，实际或假想的对象参与行为（例如，标本送，设备的要求，等等。）
	 * 。在Observation.value通常不指定，因为意图是测量血糖，测量血糖在一个特定的范围内。 （以下但与目标比较）。
	 * 
	 * 在请求的心情，一种意图，作者的请求：“请测量血糖。”参与确定实际和假想中的行为涉及人民群众，尤其是为了砂矿和指定的填充物，
	 * 以及实际或假想的对象涉及的行为
	 * （例如，标本送，设备要求等）。在Observation.value通常不指定，因为秩序是不测量血糖在一个特定的范围内。
	 * 
	 * 在事件的情绪，撰文指出：“血糖测定”。参与实际参与行为的人，实际参与对象（例如，标本，设施，设备）。
	 * Observation.value是实际获得的价值（例如，80毫克/升，或<15毫克/升）。
	 * 
	 * 事件规范（标准不应与混淆）的心情，笔者认为“获得血糖”可能具有一定的价值的结果（范围）的某一类。参与约束的标准，例如，一个特定的病人。
	 * Observation.value是的范围，在该准则将举行（例如：> 180 mg / dL或200-300毫克/升）。
	 * 
	 * 在目标心情（的标准），作者指出，“我们的目标是能够获得与给定值（范围）的血糖。”参股意向的情绪，特别是笔者的目标，并为他们的目标是取得病人的。
	 * Observation.value是范围内达到的目标时，它定义（如80-120毫克/分升）。
	 */
	@ManyToOne
	@JoinColumn(name = "classCode_id")
	private CodedSimpleValue moodCode;
	/**
	 * A unique identifier for the Act.
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * Successful communication only requires that an act have a single
	 * identifier assigned to it. However, it is recognized that as different
	 * systems maintain different databases, there may be different instance
	 * identifiers assigned by different systems.
	 * 
	 * 成功的沟通只需要一个行为有一个单一的标识符分配给它。然而，它认识到，不同的系统维护不同的数据库，有可能是由不同的系统分配不同的实例标识符。
	 */
	private DSET<II> id;

	/**
	 * The particular kind of Act that the Act-instance represents within its
	 * class.
	 * 
	 * 一种特别法，该法实例在其类代表。
	 * 
	 * 
	 * UsageConstraint:
	 * 
	 * Act.code, if used, SHALL be a specialization of the Act.classCode.
	 * 
	 * act.code，如果使用，应是一个专业化的Act.classCode。
	 * 
	 * UsageNotes:
	 * 
	 * Act.code is not a required attribute of Act. Rather than naming the kind
	 * of Act using an Act.code, one can specify the Act using only the class
	 * code and other attributes and properties of the Act. In general and more
	 * commonly, the kind of Act is readily specified by an ActRelationship
	 * specifying that this Act instantiates another Act in definition mood.
	 * Even without reference to an act definition, the act may be readily
	 * described by other attributes, ActRelationships and Participations. For
	 * example, the kind of SubstanceAdministration may be readily described by
	 * referring to the specific drug, as the Participation of an Entity
	 * representing that drug.
	 * 
	 * This attribute defines a specific sub-type of a given Act type
	 * (determined by the "classCode" attribute). It allows the use of rich
	 * terminologies such as LOINC and SNOMED to represent sub-types of the
	 * limited set of Act types defined by "classCode."
	 * 
	 * Act.classCode and Act.code are not modifiers of each other. The Act.code
	 * concept should imply the Act.classCode concept. For a negative example,
	 * it is not appropriate to use an Act.code "potassium" together with and
	 * Act.classCode for "laboratory observation" to somehow mean
	 * "potassium laboratory observation" and then use the same Act.code for
	 * "potassium" together with Act.classCode for "medication" to mean
	 * "substitution of potassium". This mutually modifying use of Act.code and
	 * Act.classCode is not permitted.
	 * 
	 * act.code不是法所需的属性。而不是命名的法令使用Act.code，可以指定该法仅使用类的代码和其他属性和属性的法案。
	 * 在一般较为普遍的一种行为很容易被指定由指定该法实例另一个法
	 * “中定义的心情ActRelationship。即使没有行为的定义，可以很容易描述的行为，由其他属性
	 * ，ActRelationships和参与。例如，样的SubstanceAdministration可能很容易被描述
	 * ，指特定的药物，作为一个代表该药物的实体参与。
	 * 
	 * 该属性定义一个特定的行为类型（“classCode”属性确定）一个特定的子类型。它允许使用，如丰富的LOINC用语，，
	 * SNOMED代表法定义类型的有限子类型“classCode。”
	 * 
	 * Act.classCode和Act.code是不是对方的修饰符。的Act.code的理念应该意味着Act.classCode的概念。
	 * 对于一个反面的例子
	 * ，它是不宜使用Act.code“钾”连同“实验室观察”Act.classCode，以某种方式的意思是“钾实验室观察”，然后使用“钾
	 * ”一起同Act.code
	 * Act.classCode“换汤不换药”的意思是“钾替代”。这的Act.code和Act.classCode相互修改的使用是不允许的。
	 * 
	 * 
	 * DesignComments:
	 * 
	 * The superstructure of the ActCode domain should reflect the structure of
	 * ActClass domain, in order that individual codes or externally referenced
	 * vocabularies within ActCode be subordinated to the ActClass structure.
	 * 
	 * Explain criteria for when it would be appropriate to use code rather than
	 * ActRelationship.
	 * 
	 * 上层建筑的ActCode域应该反映的，个人代码或外部引用的词汇，在ActCode服从的ActClass结构为了结构ActClass域的。
	 * 
	 * 解释时，这将是适当的使用的代码，而不是ActRelationship标准。
	 * 
	 * 
	 * Examples:
	 * 
	 * Physical examination, serum potassium, inpatient encounter, charge
	 * financial transaction, etc.
	 * 
	 * 体格检查，血清钾，住院相遇，负责金融交易等。
	 */
	@ManyToOne
	@JoinColumn(name = "code_id")
	private ConceptDescriptor code;
	/**
	 * An indicator specifying that the Act statement is a negation of the Act
	 * in Event mood as described by the descriptive attributes.
	 * 
	 * 指定该法案的声明是否定的描述属性描述事件的情绪作为一个指标。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The actionNegationInd works as a negative existence quantifier on the
	 * actual, intended or described Act event. In Event mood, it indicates the
	 * defined act did not occur. In Intent mood, it indicates the defined act
	 * is not intended/desired to occur. In Criterion mood, it indicates that
	 * the condition is based on the non-occurrence of the event. It is
	 * nonsensical to have a negationInd of true for acts with a mood of
	 * definition.
	 * 
	 * The actionNegationInd negates the Act as described by the descriptive
	 * properties (including Act.code, Act.effectiveTime, Observation.value,
	 * Act.doseQty, etc.) and any of its components. The document characteristic
	 * properties such as Act.id, Act.moodCode, Act.confidentialityCode, and
	 * particularly the Author-Participation are not negated. These document
	 * characteristic properties always have the same meaning: i.e., the author
	 * remains to be the author of the negative observation. Also, most
	 * ActRelationships (except for components) are not included in the
	 * negation. Refer to the attribute isDocumentCharacteristic property and
	 * the ActRelationshipType and ParticipationType code system
	 * isDocumentCharacteristic properties for specific guidance.
	 * 
	 * For example, a highly confidential order written by Dr. Jones, to
	 * explicitly not give "succinyl choline" for the "reason" (ActRelationship)
	 * of a history of malignant hyperthermia (Observation) negates the
	 * descriptive properties "give succinyl choline" (Act.code), but it is
	 * still positively an order and written by Dr. Jones and for patient John
	 * Smith, and the reason for this order is the patient's history of
	 * malignant hyperthermia.
	 * 
	 * However, additional detail in descriptive attributes will be part of the
	 * negation which then limits the effectiveness of the negated statement.
	 * For example, had the order "not to give a substance" included a
	 * doseQuantity, it would mean that the substance should not be given at
	 * that particular dose (but any other dose might still be O.K.).
	 * 
	 * An act statement with actionNegationInd is still a statement about the
	 * specific fact described by the Act. For instance, a negated
	 * "patient had an appendectomy on July 1" means that the author positively
	 * denies that appendectomy occurred on July 1, and that he takes the same
	 * responsibility for such statement and the same requirement to have
	 * evidence for such statement than if he had not used negation. Conversely,
	 * the action negation indicator does not just negate that the fact was
	 * affirmed or that the statement had been made. This holds for all moods in
	 * the same way, e.g., a negated order is an order not to do the described
	 * act, not just the lapidary statement that there is no such order. Such
	 * lapidary statements are handled by negating the control act that created
	 * the subject act. I.e.
	 * "An order of this type (DEFN mood) with an author of Dr. Smith was not created."
	 * 
	 * Note that for Observations, actionNegationInd indicates that the act
	 * itself did not occur. I.e. no observation took place. To indicate that an
	 * observation did occur but the finding was negative, use
	 * Observation.valueNegationInd.
	 * 
	 * 
	 * 作为一个实际的，有意或描述法事件的负面存在量词该actionNegationInd工作。在事件的情绪，它表示定义的行为并没有出现。在意向书的心情，
	 * 表示不打算/期望定义的行为发生。在标准的心情，它表明，事件不发生的基础条件。这是荒谬的行为与情绪的定义有一个真正的negationInd。
	 * 
	 * actionNegationInd否定的描述属性（包括Act.code，Act.effectiveTime，Observation.value，
	 * Act.doseQty等）和其任何组件的行为。不否定的文件特征属性，如Act.id，Act.moodCode，Act.
	 * confidentialityCode
	 * ，特别是作者参与。这些文件特征属性始终具有相同的含义：即，笔者仍然是负面观察作者。此外，大多数ActRelationships
	 * （组件除外），不包括在否定的。
	 * 请参阅属性isDocumentCharacteristic的财产和ActRelationshipType的和具体指导ParticipationType代码系统isDocumentCharacteristic属性
	 * 。
	 * 
	 * 例如，琼斯博士撰写的一个高度机密的命令，没有明确地给“理由”历史的恶性高热（观察）（ActRelationship）“琥珀胆碱”否定的描述属性“
	 * 给予琥珀胆碱”（Act.代码），但它仍然是积极的订单，并书面琼斯博士和约翰·史密斯病人，这个命令的原因是恶性高热病人的历史。
	 * 
	 * 然而，在描述性属性的更多细节将是部分否定，然后限制的否定声明的有效性。例如，为了“不给的物质”包括1
	 * doseQuantity，就意味着该物质不应该在特定剂量（但可能仍然是确定任何其他剂量）。
	 * 
	 * 一个与actionNegationInd行为的声明仍然是一个由该法中所描述的具体事实的声明。例如，一个否定的“病人阑尾7月1日”是指，
	 * 积极撰文否认发生于7月1日
	 * ，阑尾切除术，和他这样的语句，同样的要求同样的责任，有比这些声明的证据，他没有使用过的否定。相反，行动否定指标并不只是否定这一事实被确认
	 * ，或已作出声明
	 * 。它包含所有的情绪在以同样的方式，例如，一个否定的顺序是为了不使所描述的行为，不只是宝石的声明中，有没有这样的顺序。否定创建主体行为的控制行为
	 * ，如宝石报表处理。即“这种类型的顺序与史密斯博士撰文（DEFN心情）没有被创建。”
	 * 
	 * 请注意观察，actionNegationInd表明，这一行为本身并没有出现。即没有观察发生。为了表明观察确实发生，但结果是负的，
	 * 使用Observation.valueNegationInd。
	 * 
	 * 
	 * When used with event mood, allows communicating
	 * "Surgery was not performed" or "Consent was not given". When used in
	 * order mood, allows communicating "Do not administer this substance". When
	 * used in EVN.CRIT mood allows you to say
	 * "If the patient is not admitted . . ."
	 * 
	 * 当事件的情绪，让沟通“手术是不执行”或“同意，不给”。为了情绪时，可以沟通“不要管理这种物质”。当使用EVN.CRIT心情让你说“如果病人不承认
	 * ......”
	 * 
	 */
	@ManyToOne
	@JoinColumn(name = "actionNegationInd_id")
	private datatypes.r2.foundation.impl.Boolean actionNegationInd;
	/**
	 * A character string containing a formal language expression that specifies
	 * how the Act's attributes are, should be, or have been derived from input
	 * parameters associated with derivation relationships.
	 * 
	 * 一个字符串，其中包含一个正式的语言表达，指定法“的属性如何，是应该的，或已经从输入参数推导关系的。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * Derived observations can be defined through association with other
	 * observations using ActRelationships of type "derivation." For example, to
	 * define a derived observation for Mean Corpuscular Hemoglobin (MCH) one
	 * will associate the MCH observation with a Hemoglobin (HGB) observation
	 * and a Red Blood cell Count (RBC) observation: the derivation expression
	 * value encodes the formula: MCH = HGB / RBC.
	 * 
	 * 派生意见，可与其他使用类型ActRelationships的意见“推导定义。”通过协会例如，定义为平均红细胞血红蛋白含量（MCH）与血红蛋白（
	 * HGB）中观察和红细胞计数（RBC）的观察，人们便会联想妇幼保健院观察得出的观察：推导表达式的值编码公式：妇幼保健=血红蛋白/红细胞。
	 * 
	 * 
	 * FormalConstraint:
	 * 
	 * The derivation expression is represented as a character string.
	 * 
	 * 推导表达式表示为一个字符串。
	 * 
	 * OpenIssue:
	 * 
	 * The syntax of that expression is yet to be fully specified. Update status
	 * of this effort.
	 * 
	 * 该表达式的语法是尚未被完全指定。这一努力的更新状态。
	 */
	@ManyToOne
	@JoinColumn(name = "derivationExpr_id")
	private StringSimple derivationExpr;
	/**
	 * A word or phrase by which a specific Act may be known among people.
	 * 
	 * 人与人之间的具体行政行为可称为一个单词或词组。
	 * 
	 * UsageNotes:
	 * 
	 * This is not a formal identifier but rather a human-recognizable common
	 * name. However it is similar to the id attribute in that it refers to a
	 * specific Act rather than a 'kind' of act. (For definition mood, the title
	 * refers to that specific definition, rather than to a broad category that
	 * might be conveyed with Act.code.)
	 * 
	 * 这不是一个正式的标识符，而是一个人辨认的通用名称。然而，它是类似的id属性，它是指一个特定的法令，而不是一个样“的行为。
	 * （对于情绪的定义，标题是指特定的定义，而不是可能被与Act.code传达一个广泛的类别。）
	 * 
	 * Examples:
	 * 
	 * Name of a research study (e.g., "Scandinavian Simvastatin Study"), name
	 * of a court case (e.g., "Brown v. Board of Education"), name of another
	 * kind of work project or operation. For acts representing documents, this
	 * is the title of the document.
	 * 
	 * 一项研究名称（例如，“斯堪的纳维亚辛伐他汀研究”），法院案件的名称（例如，“布朗诉教育委员会”），另一种工作项目或操作的名称。为代表文件的行为，
	 * 这是文件的标题。
	 * 
	 * FormalConstraint:
	 * 
	 * Previous to release 2.05 of the RIM, this attribute bore the datatype ST.
	 * From release 2.05 onwards, the datatype was extended to a constrained
	 * restriction of the ED datatype. The constraints to be imposed are
	 * identical to those for the ST datatype, except that the mediaType shall
	 * be "text/x-hl7-title+xml" or "text/plain". The intent is to allow
	 * sufficient mark-up to convey the semantics of scientific phrases, such as
	 * chemical compounds. This markup must not be used to convey simple display
	 * preferences. The default mediaType should be "text/plain".
	 * 
	 * 此属性在此之前发布的RIM2.05口径的数据类型ST。从2.05版本开始，数据类型扩展到了教育署的数据类型的约束限制。
	 * 施加的限制是相同的数据类型为ST除外，mediaType应是“text/x-hl7-title+ xml”或“text /
	 * plain的”。这样做的目的是允许足够的标记
	 * ，传达科学短语的语义，如化合物。这个标记不能用来传递简单的显示偏好。默认mediaType应该是“text / plain的”。
	 */
	@ManyToOne
	@JoinColumn(name = "title_id")
	private EncapsulatedData title;
	/**
	 * Definition: A renderable textual or multimedia description (or reference
	 * to a description) of the complete information which would reasonably be
	 * expected to be displayed to a human reader conveyed by the Act.
	 * 
	 * 一个可渲染的完整的信息，将合理预期，显示人类读者转达了该法案的文本或多媒体说明（或描述）。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The content of the description is not considered part of the functional
	 * information communicated between computer systems. For Acts that involve
	 * human readers and performers, however, computer systems must show the
	 * Act.text field to a human user, who has responsibility for the activity;
	 * or at least must indicate the existence of the Act.text information and
	 * allow the user to see that information.
	 * 
	 * Free text descriptions are used to help individuals interpret the content
	 * and context of acts, but all information relevant for automated functions
	 * SHALL be communicated using the proper attributes and associated objects.
	 * 
	 * A user SHOULD be able to read Act.text alone, without seeing any of the
	 * encoded information, and have no risk of misinterpreting or lacking full
	 * understanding of the full content of the Act. For example, II.root, or
	 * CD.codeSystem would not normally be displayed to a human and thus would
	 * not need to be exposed as part of Act.text.
	 * 
	 * The rendering is expected to include all 'descendent' ActRelationships
	 * and Participations, recursively navigating child Acts as exposed in that
	 * particular 'snapshot.' However, there are several data elements which are
	 * NOT expected to be included in the rendering. These are
	 * 
	 * Component Sections (ActRelationship=COMP, classCode <= DOCSECT)
	 * 
	 * The title attribute
	 * 
	 * Anything attached to ActRelationship=XFRM)
	 * 
	 * Previous versions (ActRelationship=RPLC)
	 * 
	 * Act.text MAY include information that is not in the other
	 * attributes/associations, but SHALL include all information that is in
	 * such attributes or associations, with the exception of those identified
	 * above.
	 * 
	 * Act.text SHALL NOT be used for the sharing of computable information.
	 * Computable information SHALL be conveyed using discrete attributes. Any
	 * information which Act.text contains not elsewhere exposed in encoded
	 * information will be opaque to computer systems. For this reason, Act.text
	 * SHALL not be used to contain information which negates or significantly
	 * modifies the understanding of information encoded in discrete attributes.
	 * 
	 * To communicate "supplemental text," an act relationship (e.g. "component"
	 * or "subject of") should be created to a separate Act with a bare Act.text
	 * attribute to convey the supplemental information, possibly with a code
	 * indicating "annotation" or some similar concept.
	 * 
	 * 描述的内容不被视为计算机系统之间沟通的信息功能的一部分。涉及人类的读者和表演者的行为，然而，电脑系统必须显示Act.text领域给人类用户，
	 * 谁都有责任的活动;或至少必须指出的存在的Act.text信息，并允许用户看到这些信息。
	 * 
	 * 免费的文字说明是用来帮助个人解释的行为的内容和背景，但应通知所有相关的自动化功能的信息，使用正确的属性和相关联的对象。
	 * 
	 * 用户应该能够独自阅读Act.text，没有看到任何的编码信息，并没有任何风险的误解或缺乏充分了解该法案的全部内容。例如，II.root，或CD.
	 * codeSystem的将不能正常显示一个人，因此不会被作为Act.text的部分需要暴露。
	 * 
	 * 渲染预计将包括所有的“后代”ActRelationships和参与，递归航行儿童行为暴露，特别是在“快照”。然而，有几个数据，
	 * 预计不会被包括在渲染的元素。这些都是
	 * 
	 * 组件第（ActRelationship =补偿，classCode <= DOCSECT，）
	 * 
	 * 标题属性
	 * 
	 * 什么连接到ActRelationship = XFRM）
	 * 
	 * 以前的版本（ActRelationship =反相高效液相色谱）
	 * 
	 * act.text可能包括信息，是不是在其他属性/协会，但应包括所有的信息是，在这样的属性或协会，除上述确定的。
	 * 
	 * act.text不能使用的可计算信息的共享。使用离散属性可计算的信息应传达。任何信息Act.text包含其他未编码信息公开是不透明的计算机系统。
	 * 出于这个原因，Act.text将不会被用来包含的信息而否定或大幅修改离散属性的编码信息的理解。
	 * 
	 * 沟通“的补充文本”的行为的关系（如“组件”或“主题”）应与裸Act.text属性创建一个单独的法令传达，可能与代码，表示“注释”或补充信息，
	 * 一些类似的概念。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * Clarify strength of
	 * "Act.text SHALL NOT be used for the sharing of computable information":
	 * should this be a constraint?
	 * 
	 * 澄清不得用于可计算信息的共享使用“力量”Act.text：这应该是一个约束？
	 * 
	 * Examples:
	 * 
	 * For act definitions, the Act.text can contain textbook-like information
	 * about that act. For act orders, the description will contain particular
	 * instructions pertaining only to that order.
	 * 
	 * 对于行为的定义，Act.text可以包含类似的教科书有关该行为的信息。对于订单的行为，说明将包含只限于特别说明的顺序。
	 * 
	 */
	@ManyToOne
	@JoinColumn(name = "text_id")
	private EncapsulatedData text;
	/**
	 * Definition: The state of the Act.
	 * 
	 * 该法的状态。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The status reflects the state of the activity. In the case of an
	 * Observation, this is the status of the activity of observing (e.g.,
	 * "new," "complete," "cancelled"), not the status of what is being observed
	 * (e.g., disease status, "Active" allergy to penicillin). To convey the
	 * status of the subject being observed, consider coordinating it into the
	 * code or value attribute of the Observation or using a related
	 * Observation.
	 * 
	 * 6.5.10 Act.effectiveTime :: QSET<TS> (0..1) Property conformance: U
	 * 
	 * Definition: The clinically or operationally relevant time of an act,
	 * exclusive of administrative activity.
	 * 
	 * 状态反映了国家的活动。在观察的情况下，这是观测活动的状态（例如，“新”，“完成”，“取消”），而不是被观测的状态（例如，疾病状态，“主动”
	 * 过敏青霉素）。传达的被观察的主体地位，考虑代码或值属性的观察到协调或使用相关的观察。
	 * 
	 */
	@ManyToOne
	@JoinColumn(name = "statusCode_id")
	private CodedSimpleValue statusCode;
	/**
	 * Definition: The clinically or operationally relevant time of an act,
	 * exclusive of administrative activity.
	 * 
	 * 临床或业务有关的行为，行政活动的独家。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The effectiveTime is also known as the "primary" time (Arden Syntax) or
	 * the "biologically relevant time" (HL7 v2.x). This attribute is
	 * distinguished from activityTime.
	 * 
	 * For observations, the time of the observation activity may be much later
	 * than the time of the observed feature. For instance, in a Blood Gas
	 * Analysis (BGA), a result will not be available for several minutes after
	 * the specimen was taken, meanwhile the patient's physiological state may
	 * have changed significantly.
	 * 
	 * For essentially physical activities (surgical procedures,
	 * transportations, etc.), the effective time is the time of interest for
	 * the Act's intention, i.e., since the intention of a transportation is to
	 * deliver a payload from location A to B, the effectiveTime is the time
	 * this payload is underway from A to B. However, the Act usually also
	 * includes accidental work which is necessary to perform the intention of
	 * the Act, but is not relevant for the Act's purpose.
	 * 
	 * For example, the time a driver needs to go to the pick-up location A and
	 * then return from drop-off location B to some home base, is included in
	 * the physical activity (as activityTime), but it does not matter from the
	 * perspective of the payload's transportation and is excluded from
	 * effectiveTime. Another example: a person's work hours (effectiveTime) may
	 * be from 8 AM to 5 PM, no matter whether that person needs 10 minutes for
	 * the commute or 2 hours. The commute is necessary to be at work, but it is
	 * not part of the working time.
	 * 
	 * 的effectiveTime也被称为“主”的时间（雅顿语法）或“生物有关时间”（HL7的2.x版）。此属性是区别于activityTime。
	 * 
	 * 为观测，观测活动的时间可能要晚得多的时间所观察到的特征。例如，在血气分析（BGA）封装，因此不会是几分钟后的标本，
	 * 同时病人​​的生理状态可能显着改变。
	 * 
	 * 基本上体力活动（外科手术，运输等），有效时间是利益的时间，因为该法案的意图，即运输的意向是提供有效载荷从位置A到B，
	 * effectiveTime是有效载荷是正在从A，B。但是，该法通常还包括意外的工作，这是必要的，以执行该法案的目的，但并不是有关该法案的目的。
	 * 
	 * 例如，驱动程序需要的时间到A，然后从落客地点B返回到一些大本营，在体力活动（作为activityTime）回升的位置，但不要紧，
	 * 从这个角度有效载荷的运输和从effectiveTime排除
	 * 。另一个例子：一个人的工作小时（effectiveTime）可能是从8点到下午5点，不管这个人是否需要通勤或2小时10分钟
	 * 。通勤是必要的是，在工作，但它是不是工作时间的一部分。
	 * 
	 * 
	 * Examples:
	 * 
	 * For clinical Observations, the effectiveTime is the time at which the
	 * observation holds (is effective) for the patient.
	 * 
	 * For contracts, the effectiveTime is the time for which the contract is in
	 * effect.
	 * 
	 * For consents, the effectiveTime is the time for which the consent is
	 * valid.
	 * 
	 * For substance administrations, the effective time is the time over which
	 * the substance is to be administered, including the frequency of
	 * administration (e.g., TID for 10 days)
	 * 
	 * For a surgical procedure (operation), the effectiveTime is the time
	 * relevant for the patient, i.e., between incision and last suture.
	 * 
	 * For transportation acts, the effective time is the time the transported
	 * payload is en route.
	 * 
	 * For patient encounters, this is the "administrative" time, i.e., the
	 * encounter start and end date required to be chosen by business rules, as
	 * opposed to the actual time the healthcare encounter related work is
	 * performed.
	 * 
	 * 临床观察，effectiveTime是时间的观察认为是有效的病人。
	 * 
	 * 对于合同，effectiveTime是合同生效的时间。
	 * 
	 * 同意书，effectiveTime同意是有效的时间。
	 * 
	 * 物质的管理部门，有效时间是时间，超过该物质加以管理，包括管理的频率（例如，10天工贸署）
	 * 
	 * 对于手术（操作），effectiveTime是与病人之间的切口，最后缝合，即有关的时间。
	 * 
	 * 运输行为，有效时间是运送有效载荷是途中的时间。
	 * 
	 * 病人接触，这是“行政”的时间，即遭遇的开始和结束日期，业务规则，反对执行相关工作的医疗遇到的实际时间须选择。
	 */
	private QSET<TS> effectiveTime;
	/**
	 * Definition: A time expression specifying when an Observation, Procedure,
	 * or other Act occurs, or, depending on the mood, is supposed to occur,
	 * scheduled to occur, etc. The activityTime includes the times of component
	 * actions (such as preparation and clean-up). For Procedures and
	 * SubstanceAdministrations, the activityTime can provide a needed
	 * administrative function by providing a more inclusive time to be
	 * anticipated in scheduling.
	 * 
	 * 指定观察程序，或其他行为时发生，或根据心情，一时间表达，应该发生，预计发生等activityTime包括组件行动的时间（如准备和清理）
	 * 。对于程序和SubstanceAdministrations
	 * ，activityTime可以提供一个需要的行政职能，通过提供一个更具包容性的时间，预计在调度。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The activityTime is primarily of administrative rather than clinical use.
	 * The clinically relevant time is the effectiveTime. When an observation of
	 * a prior symptom is made, the activityTime describes the time the
	 * observation is made, as opposed to effectiveTime which is the time the
	 * symptom is reported to have occurred. Thus the activityTime may be
	 * entirely different from the effectiveTime of the same Act. However, even
	 * apart from clinical use cases, designers should first consider
	 * effectiveTime as the primary relevant time for an Act.
	 * 
	 * ActivityTime indicates when an Act occurs, not when it is recorded. Many
	 * applications track the time an observation is recorded rather than the
	 * precise time during which an observation is made, in which case
	 * Participation.time (e.g. of the Author) should be used. These recorded
	 * observations can take place during an encounter, and the time of the
	 * encounter often provides enough information so that activityTime isn't
	 * clinically relevant.
	 * 
	 * ActivityTime is a descriptive attribute: like effectiveTime, it always
	 * describes the Act event as it does or would occur. For example, when a
	 * procedure is requested, the activityTime describes the requested total
	 * time of the procedure, which may differ from the time recorded for the
	 * resulting event. By contrast, the author Participation.time is inert,
	 * i.e., author participation time on an order specifies when the order was
	 * written and has nothing to do with when the event might actually occur.
	 * 
	 * 在activityTime是主要的，而不是临床使用的管理。临床相关的时间是的effectiveTime。当一个前症状的观察，
	 * activityTime介绍时间的观察
	 * ，反对的effectiveTime这是据报道，发生症状的时间。因此，activityTime可能是完全从同法effectiveTime不同的
	 * 。然而，甚至除了从临床使用的情况下，设计师首先应该考虑作为主要的一项法令，有关时间effectiveTime。
	 * 
	 * ActivityTime表示一种行为发生时，而不是当它被记录。许多应用程序跟踪观察记录，而不是精确的时间的观察，在这种情况下，
	 * Participation .time（例如笔者）应使用。记录的这些意见可以采取过程中遇到的地方，经常遇到的时间提供足够的信息，所以，
	 * activityTime是没有临床相关。
	 * 
	 * ActivityTime是一个描述性的属性：像effectiveTime，它总是描述法“事件，因为它或将发生。例如，当一个程序被请求时，
	 * 的activityTime描述程序的请求的总时间
	 * ，从产生的事件记录的时间可能会有所不同。相比之下，笔者Participation.time是惰性的，
	 * 即指定时，为了写作者为了参与时间和事件时，实际上可能发生无关。
	 */
	private QSET<TS> activityTime;
	/**
	 * Definition: The point in time at which information about Act-instance
	 * (regardless of mood) first became available to a system reproducing this
	 * Act. The availabilityTime is metadata describing the record, not the Act.
	 * 
	 * 约法实例信息（不管心情）首次成为可用的系统，音响本法的时间点。 availabilityTime是元数据描述的记录，而不是法。
	 * 
	 * UsageNotes:
	 * 
	 * The availabilityTime is added (or changed) by any system that receives
	 * this Act, and is not attributed to the author of the act statement (it
	 * would not be included in the material the author would attest to with a
	 * signature). The system reproducing the Act is often not the same as the
	 * system originating the Act, but a system that received this Act from
	 * somewhere else, and, upon receipt of the Act, values the availabilityTime
	 * to convey the time since the users of that particular system could have
	 * known about this Act-instance.
	 * 
	 * A system evaluates availabilityTime on receipt (or creation) of
	 * information, and must be able to produce the availabilityTime of the
	 * information if and when it communicates that information further.
	 * 
	 * 添加的availabilityTime（或改变）本法的任何系统接收，并不能归因于作者的行为语句（它不会被包括在材料，笔者将证明签名）。
	 * 法音响系统往往是不作为发起该法案的系统相同
	 * ，但接受这项法令，从别的地方和系统，根据该法的收据，重视availabilityTime传达的时间，因为该特定系统的用户可能已经知道此法实例。
	 * 
	 * 对收到的信息（或创建）一个系统评估availabilityTime，必须能够产生的，如果信息availabilityTime，当它进一步传达的信息
	 * 。
	 * 
	 * 
	 * Rationale:
	 * 
	 * An Act might record that a patient had a right-ventricular myocardial
	 * infarction effective three hours ago (see Act.effectiveTime), but we may
	 * only know about this unusual condition a few minutes ago
	 * (Act.availabilityTime). Thus, any interventions from three hours ago
	 * until a few minutes ago may have assumed the more common left-ventricular
	 * infarction, which can explain why these interventions (e.g., nitrate
	 * administration) were taken, even though they may not have been
	 * appropriate in light of the more recent knowledge.
	 * 
	 * 一项法令，可能会记录病人右心室心肌梗死的有效三个小时前（见Act.effectiveTime），但我们可能只知道这个不寻常的条件下，几分钟前（
	 * Act .availabilityTime）。因此，从三个小时前，直到几分钟前的任何干预可能承担更常见的左心室心肌梗死，
	 * 这可以解释为什么采取这些干预措施 （如硝酸管理），尽管他们可能不会有适当的光更近的知识。
	 * 
	 * 
	 * DesignComments:
	 * 
	 * Clarify: Does the act acquire a new availability time with each
	 * transmission? Does this value indicate to which system it refers? Or is
	 * it always defined as the availability time for the transmitting system in
	 * the context of a message, any further transmission either dropping or
	 * overwriting it, and recording, if necessary, previous transmission times
	 * as separate observations?
	 * 
	 * Deleted text indicates availabilityTime is
	 * "attributed to the author of an act that includes or refers to the act."
	 * It is not clear why this attribute should require special conduction
	 * rules: are they different from the rules for other attributes?
	 * 
	 * 澄清：收购行为是否与每次传输一个新的可用时间？这个值显示系统，它是指？或者是它总是作为传输系统的可用性时间定义在消息的情况下，删除或覆盖它，
	 * 并记录任何进一步的传输，如果有必要，作为单独的观测先前的传输时间？
	 * 
	 * 删除的文字表明availabilityTime是“，是指行为的行为，包括作者。”目前尚不清楚为什么这个属性需要特殊的传导规则：
	 * 他们是从其他属性的规则不同？
	 */
	private TS availabilityTime;
	/**
	 * Definition: The urgency under which the Act happened, can happen, is
	 * happening, is intended to happen, or is requested/demanded to happen.
	 * 
	 * 发生，根据该法的紧迫性，都可能发生，正在发生的事情，是为了发生，或者被请求/要求发生。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is used in orders to indicate the ordered priority, and in
	 * event documentation it indicates the actual priority used to perform the
	 * act. In definition mood it indicates the available priorities, hence the
	 * open cardinality.
	 * 
	 * 订单这个属性是用来指示下令优先，并在事件的文件，它表明实际优先用于执行行为。在定义心情表示可用的优先事项，因此，开放的基数。
	 * 
	 * 
	 * Examples:
	 * 
	 * Routine, elective, emergency.
	 * 
	 * 常规，选修，紧急
	 */
	private DSET<CD> priorityCode;
	/**
	 * Definition: Constraints around appropriate disclosure of information
	 * about this Act, regardless of mood.
	 * 
	 * 围绕有关此法案的适当信息披露的限制，无论心情。
	 */
	@ManyToOne
	@JoinColumn(name = "confidentialityCode_id")
	private ConceptDescriptor confidentialityCode;
	/**
	 * Definition: An interval of integer numbers stating the minimal and
	 * maximal number of repetitions of the Act.
	 * 
	 * 一个整数区间，说明该法的重复的最小和最大数量。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is a member of the workflow control suite of attributes.
	 * 
	 * The number of repeats is additionally constrained by time. The act will
	 * repeat at least the minimal number of times and at most, the maximal
	 * number of times, unless the time exceeds the maximal Act.effectiveTime,
	 * at which point the repetitions will terminate
	 * 
	 * On an Act in Event mood, the repeatNumber is usually 1. If greater than
	 * 1, the Act represents a summary of several event occurrences occurring
	 * over the time interval described by effectiveTime. These occurrences are
	 * not otherwise distinguished.
	 * 
	 * To distinguish occurrences of acts within a sequence of repetitions, use
	 * distinct instances of Act related by ActRelationships using
	 * ActRelationship.sequenceNumber.
	 * 
	 * 该属性是一个属性的流程控制套件的成员。
	 * 
	 * 此外，重复的次数是按时间的限制。该法案将重复至少倍的最低数量最多，最大数量的时代，在这一点，除非时间超过的最大Act.effectiveTime，
	 * 重复将终止
	 * 
	 * 在事件情绪的一项法令，该repeatNumber通常为1。如果大于1，
	 * 该法案代表了几个事件的时间间隔比由effectiveTime描述发生的事件的总结。否则无法区分这些事件。
	 * 
	 * 要区分内重复序列行为的发生，使用不同使用ActRelationship.sequenceNumber
	 * ActRelationships的相关法令的实例。
	 * 
	 * 
	 * Examples:
	 * 
	 * An oral surgeon's advice to a patient after tooth extraction might be:
	 * "replace the gauze every hour for 1 to 3 times until bleeding has stopped completely."
	 * This translates to repeatNumber with low boundary 1 and high boundary 3.
	 * 
	 * 患者拔牙后口腔外科医生的意见，可能是：“更换纱布每隔一小时为1至3次，直至出血完全停止。”这意味着低边界和边界3高repeatNumber。
	 */
	private IVL<INT_NONNEG> repeatNumber;
	/**
	 * Definition: An indication that the Act is interruptible by asynchronous
	 * events.
	 * 
	 * 迹象表明，该法是由异步事件中断。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * This attribute is part of the suite of workflow control attributes. Act
	 * events that are currently active can be interrupted in various ways.
	 * Interrupting events include (1) an explicit abort request against the
	 * Act, (2) expiration of the time allotted to this Act (timeout), (3) a
	 * "through condition" ceases to hold true for this Act (see
	 * ActRelationship.checkpointCode), (4) the Act is a component with the
	 * joinCode "kill" and all other components in that same group have
	 * terminated (see Act.joinCode), and (5) a containing Act is interrupted.
	 * 
	 * If an Act receives an interrupt and the Act itself is interruptible, but
	 * it has currently active component-Acts that are non-interruptible, the
	 * Act will be interrupted when all of its currently active
	 * non-interruptible component-acts have terminated.
	 * 
	 * 此属性是一整套流程控制属性的一部分。法事件，目前正在积极以各种方式可以被打断。中断事件，包括：（1）反对该法案明确的中止请求，（2）分配法“（超时
	 * ）的时间到期，（3）”通过条件“不再担任该法案的真正（见ActRelationship.checkpointCode）
	 * （4）法是一种组件与joinCode“杀”，并在同一组的所有其他组件已终止（见Act.joinCode），，（5）包含法“被中断。
	 * 
	 * 如果一项法令，收到一个中断，该法案本身是可中断的，但它目前的活性成分是不可中断的行为，该法将被中断时，所有目前活跃的非中断组件的行为已经终止。
	 */
	@ManyToOne
	@JoinColumn(name = "interruptibleInd_id")
	private datatypes.r2.foundation.impl.Boolean interruptibleInd;
	/**
	 * Definition: Code specifying the level within a hierarchical Act
	 * composition structure and the kind of contextual information attached to
	 * composite Acts ("containers") and propagated to component Acts within
	 * those containers. The levelCode signifies the position within such a
	 * containment hierarchy and the applicable constraints.
	 * 
	 * 代码指定范围内水平分层法的组成结构和复合行为（“容器”）和传播这些容器内的组件行为的上下文信息。
	 * 该levelCode意味着在这样一个包容层次结构和适用的限制的立场。
	 * 
	 * 
	 * UsageConstraint:
	 * 
	 * The constraints applicable to a particular level may include differing
	 * requirements for participations (e.g. patient, source organization,
	 * author or other signatory), relationships to or inclusion of other Acts,
	 * documents or use of templates. The constraints pertaining to a level may
	 * also specify the permissible levels that may be contained as components
	 * of that level. Several nested levels with the same levelCode may be
	 * permitted, prohibited (or limited). Instances of the next subordinate
	 * level are usually permitted within any level but some levels may be
	 * omitted from a model and it may be permissible to skip several layers.
	 * 
	 * 适用于某一特定水平的制约，可能包括参与（如病人，源组织，作者或其他签署国），关系或列入的其他行为，文件或使用模板的不同要求。有关水平的约束，
	 * 也可以指定允许的水平 ，可作为该级别的组件中。可获准与相同levelCode几个嵌套级别，禁止（或限制）。未来下属水平的实例通常允许在任何级别，
	 * 但可以省略某些层次模型 ，它可能允许跳过几层。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * The levelCode concepts have been defined to meet specific health record
	 * transfer requirements. While these concepts are known to be applicable to
	 * some other types of transactions, they are not intended to be a complete
	 * closed list. Options exist for other sets of orthogonal levels where
	 * required to meet a business purpose (e.g. a multiple patient
	 * communication may be subdivided by a super-ordinate level of subject
	 * areas).
	 * 
	 * levelCode概念已定义，以满足特定的健康创纪录的转会要求。虽然这些概念被称为是适用于一些其他类型的交易，他们不打算成为一个完整的封闭列表。
	 * 如有需要，以满足商业目的（如多个病人沟通超级统筹水平的学科领域可细分）的正交水平等成套选项存在。
	 * 
	 * 
	 * DesignComments:
	 * 
	 * Pending deprecation decision: this attribute does not seem to have been
	 * maintained.
	 * 
	 * 弃用的决定之前，似乎并没有一直保持这个属性。
	 * 
	 * 
	 * 
	 * Examples:
	 * 
	 * The "extract level" and the "folder level" must contain data about a
	 * single individual, whereas the "multiple subject level" may contain data
	 * about multiple individuals. While "extract" can originate from multiple
	 * sources, a "folder" should originate from a single source. The
	 * "composition" level usually has a single author.
	 * 
	 * “提取水平”和“文件夹级别”必须包含有关一个人单独的数据，而“多学科水平”可能包含多个个体的数据。虽然可以来自多个来源的“提取”，“夹”
	 * 应该源于单一来源。 “组成”的水平，通常有一个单一的作者。
	 */
	@ManyToOne
	@JoinColumn(name = "levelCode_id")
	private ConceptDescriptor levelCode;
	/**
	 * Definition: An indicator specifying whether the Act can be manipulated
	 * independently of other Acts or only through a super-ordinate composite
	 * Act that has this Act as a component.
	 * 
	 * 指定该法是否可以被操纵，通过一个超级统筹复合法此法作为一个组件，独立于其他行为或仅一个指标。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * By default the independentInd should be true. An Act definition is
	 * sometimes marked with independentInd=false if the business rules would
	 * not allow this act to be ordered without ordering the containing act
	 * group.
	 * 
	 * 默认情况下，应该是真实的independentInd。有时与independentInd标记行为的定义=
	 * false如果业务规则不会允许这种行为没有订购包含行为组排列。
	 * 
	 * 
	 * 
	 * Examples:
	 * 
	 * An order may have a component that cannot be aborted independently of the
	 * other components.
	 * 
	 * 一个订单可能有一个不能被中止，独立于其他组件的组件。
	 */
	@ManyToOne
	@JoinColumn(name = "independentInd_id")
	private datatypes.r2.foundation.impl.Boolean independentInd;
	/**
	 * Definition: An indication that the Act statement as a whole, with its
	 * subordinate components has been asserted to be uncertain in some way.
	 * 
	 * 法声明，其下属的组成部分，作为一个整体已经断言是在某种程度上的不确定性的迹象。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * Uncertainty asserted using this attribute applies to the combined meaning
	 * of the Act statement established by all descriptive attributes (e.g.,
	 * Act.code, Act.effectiveTime, Observation.value,
	 * SubstanceAdministration.doseQuantity, etc.), and the meanings of any
	 * components, not uncertainty regarding the value of Observation.value or
	 * any other particular attribute. These should be specified by applying the
	 * PPD or UVP data type extensions to the specific attribute. Uncertainty
	 * regarding a quantitative measurement value must still be represented by a
	 * PPD<PQ> in the value; differential diagnoses enumerated or weighed for
	 * probability must use the UVP<CD>. The use of the uncertaintyCode is
	 * appropriate only if the entirety of the Act and its dependent Acts is
	 * questioned.
	 * 
	 * There is no relationship between uncertaintyCode and negationInd. One may
	 * be very uncertain about an event, but that does not mean that one is
	 * certain about the negation of the event.
	 * 
	 * If this attribute is left unspecified or is omitted from a particular
	 * model, it SHALL be inferred that the attribute has the semantic of
	 * “stated with no assertion of uncertainty”.
	 * 
	 * No default value shall be declared for this attribute with a semantic
	 * that differs from “stated with no assertion of uncertainty”, though
	 * defaults may be asserted that convey this semantic in any desired code
	 * system.
	 * 
	 * 使用此属性适用于描述属性的（例如，Act.code，Act.effectiveTime，Observation.value，
	 * SubstanceAdministration
	 * .doseQuantity等）的设立法“语句的组合意义的不确定性断言，任何组件的含义，而不是有关的Observation
	 * .value或任何其他特定属性值的不确定性。这些应注明采用的PPD或UVP数据类型扩展到特定的属性。定量测量值的不确定性仍然必须由值PPD<PQ>
	 * 代表列举或打压的概率的鉴别诊断必须使用的UVP<CD>。使用uncertaintyCode是适当的，只有当该法完全依赖于它的行为提出了质疑。
	 * 
	 * 是之间没有uncertaintyCode和negationInd的关系。一个可能是非常关注事件的不确定性，但并不意味着，一个是对某些事件的否定。
	 * 
	 * 如果此属性未指定或省略，从一个特定的模式，它应推断该属性有“没有断言说的不确定性”的语义。
	 * 
	 * 从“没有不确定性断言表示：”不同的语义，应宣布这个属性没有默认值，默认值虽然可以断言，在任何所需的代码系统传达这个语义。
	 * 
	 * 
	 * Examples:
	 * 
	 * Patient might have had a cholecystectomy procedure in the past, but
	 * isn&apost sure: stated with uncertainty. Patient stipulates a
	 * cholecystectomy procedure in the past: stated with no assertion of
	 * uncertainty.
	 * 
	 * 病人可能有胆囊切除术过程，在过去的一个，但不是与apost肯定的：表示具有不确定性。病人的规定，在过去的胆囊切除术过程：有没有不确定性断言说。
	 */
	@ManyToOne
	@JoinColumn(name = "uncertaintyCode_id")
	private ConceptDescriptor uncertaintyCode;
	/**
	 * Definition: The motivation, cause, or rationale of an Act, when such
	 * rationale is not reasonably represented as an ActRelationship of type
	 * "has reason" linking to another Act.
	 * 
	 * 的动机，原因，或一项法令的理由，这种理由是不合理作为一个类型ActRelationship的代表“有原因”连接到另一法。
	 * 
	 * 
	 * UsageNotes:
	 * 
	 * Most reasons for acts can be clearly expressed by linking the new Act to
	 * another prior Act record using an ActRelationship of type "has reason."
	 * This simply states that the prior Act is a reason for the new Act (see
	 * ActRelationship). The prior act can then be a specific existing act or a
	 * textual explanation. This works for most cases, and the more specific the
	 * reason data is, the more should this reason ActRelationship be used
	 * instead of the reasonCode.
	 * 
	 * The reasonCode remains as a place for common reasons that are not related
	 * to a prior Act or any other condition expressed in Acts. Indicators that
	 * something was required by law or was on the request of a patient may
	 * qualify. However, if that piece of legislation, regulation, or the
	 * contract or the patient request can be represented as an Act (and they
	 * usually can), such a representation is preferable to the reasonCode.
	 * 
	 * 行为的多数原因可以明确表示，新法案的通过链接使用“有理由类型ActRelationship的另一个前法纪录。”这只是前法“是一个新法案的原因（
	 * 见ActRelationship）。之前的行为，然后可以现有一个特定的行为或文字说明。这适用于大多数情况下，更具体的数据的原因是，
	 * 更应该这的原因ActRelationship的reasonCode使用代替。
	 * 
	 * 该reasonCode仍作为事先法令或任何其他条件的行为表示不相关的常见的原因的地方。可能符合法律规定的东西，或病人的要求的指标。但是，
	 * 如果这块法律，法规或合同或病人的要求，可以作为代表法“（他们通常可以），这样的表示是可取的reasonCode。
	 * 
	 * 
	 * Examples:
	 * 
	 * Example reasons that might qualify for being coded in this field might
	 * be: "routine requirement," "infectious disease reporting requirement,"
	 * "on patient request," "required by law."
	 * 
	 * 例如，可能有资格被编码在这一领域的原因可能是：“常规要求”，“传染病报告要求，”对病人的要求，“法律规定”。
	 */
	private DSET<ConceptDescriptor> reasonCode;
	/**
	 * Definition: The primary language in which this Act statement is
	 * specified, particularly the language of the Act.text.
	 * 
	 * 在该法案声明指定的主要语言，特别的Act.text的语言。
	 */
	@ManyToOne
	@JoinColumn(name = "languageCode_id")
	private ConceptDescriptor languageCode;
	/**
	 * Definition: If true, indicates that the data conveyed by the act,
	 * including outbound associations, represent "criteria" for some other act,
	 * not a "real" act. I.e. If an Act exists with a classCode of ACT and a
	 * moodCode of RQO and isCriterionInd is true, it does not represent an
	 * order for an act. Rather, it represents a criteria that will match on all
	 * orders.
	 * 
	 * 如果情况属实，表示行为所传达的数据，包括呼出协会，代表“标准”的一些其他行为，而不是一个“真正”的行为。即如果法案存在的ACT
	 * classCode和RQO和isCriterionInd moodCode是真实的，它并不代表秩序的行为。相反，它代表了一种标准，将匹配所有订单。
	 * 
	 * 
	 * Constraint: Act-relationships directed to any Act with
	 * "isCriterionInd=true" SHALL have "conductible=false" unless the source
	 * Act also has isCriterionInd=true.
	 * 
	 * 约束：直接与“isCriterionInd=真正的”法“的任何行为的关系应”导水=假“，除非源法”也有isCriterionInd=。
	 */
	@ManyToOne
	@JoinColumn(name = "isCriterionInd_id")
	private datatypes.r2.foundation.impl.Boolean isCriterionInd;

	private List<ActRelationship> inboundRelationship = new ArrayList<ActRelationship>();
	private List<ActRelationship> outboundRelationship = new ArrayList<ActRelationship>();

	private List<Participation> participation = new ArrayList<Participation>();

	public long getActId() {
		return actId;
	}

	public void setActId(long actId) {
		this.actId = actId;
	}

	public CodedSimpleValue getClassCode() {
		return classCode;
	}

	public void setClassCode(CodedSimpleValue classCode) {
		this.classCode = classCode;
	}

	public CodedSimpleValue getMoodCode() {
		return moodCode;
	}

	public void setMoodCode(CodedSimpleValue moodCode) {
		this.moodCode = moodCode;
	}

	public DSET<II> getId() {
		return id;
	}

	public void setId(DSET<II> id) {
		this.id = id;
	}

	public ConceptDescriptor getCode() {
		return code;
	}

	public void setCode(ConceptDescriptor code) {
		this.code = code;
	}

	public datatypes.r2.foundation.impl.Boolean getActionNegationInd() {
		return actionNegationInd;
	}

	public void setActionNegationInd(
			datatypes.r2.foundation.impl.Boolean actionNegationInd) {
		this.actionNegationInd = actionNegationInd;
	}

	public StringSimple getDerivationExpr() {
		return derivationExpr;
	}

	public void setDerivationExpr(StringSimple derivationExpr) {
		this.derivationExpr = derivationExpr;
	}

	public EncapsulatedData getTitle() {
		return title;
	}

	public void setTitle(EncapsulatedData title) {
		this.title = title;
	}

	public EncapsulatedData getText() {
		return text;
	}

	public void setText(EncapsulatedData text) {
		this.text = text;
	}

	public CodedSimpleValue getStatusCode() {
		return statusCode;
	}

	public void setStatusCode(CodedSimpleValue statusCode) {
		this.statusCode = statusCode;
	}

	public QSET<TS> getEffectiveTime() {
		return effectiveTime;
	}

	public void setEffectiveTime(QSET<TS> effectiveTime) {
		this.effectiveTime = effectiveTime;
	}

	public QSET<TS> getActivityTime() {
		return activityTime;
	}

	public void setActivityTime(QSET<TS> activityTime) {
		this.activityTime = activityTime;
	}

	public TS getAvailabilityTime() {
		return availabilityTime;
	}

	public void setAvailabilityTime(TS availabilityTime) {
		this.availabilityTime = availabilityTime;
	}

	public DSET<CD> getPriorityCode() {
		return priorityCode;
	}

	public void setPriorityCode(DSET<CD> priorityCode) {
		this.priorityCode = priorityCode;
	}

	public ConceptDescriptor getConfidentialityCode() {
		return confidentialityCode;
	}

	public void setConfidentialityCode(ConceptDescriptor confidentialityCode) {
		this.confidentialityCode = confidentialityCode;
	}

	public IVL<INT_NONNEG> getRepeatNumber() {
		return repeatNumber;
	}

	public void setRepeatNumber(IVL<INT_NONNEG> repeatNumber) {
		this.repeatNumber = repeatNumber;
	}

	public datatypes.r2.foundation.impl.Boolean getInterruptibleInd() {
		return interruptibleInd;
	}

	public void setInterruptibleInd(
			datatypes.r2.foundation.impl.Boolean interruptibleInd) {
		this.interruptibleInd = interruptibleInd;
	}

	public ConceptDescriptor getLevelCode() {
		return levelCode;
	}

	public void setLevelCode(ConceptDescriptor levelCode) {
		this.levelCode = levelCode;
	}

	public datatypes.r2.foundation.impl.Boolean getIndependentInd() {
		return independentInd;
	}

	public void setIndependentInd(
			datatypes.r2.foundation.impl.Boolean independentInd) {
		this.independentInd = independentInd;
	}

	public ConceptDescriptor getUncertaintyCode() {
		return uncertaintyCode;
	}

	public void setUncertaintyCode(ConceptDescriptor uncertaintyCode) {
		this.uncertaintyCode = uncertaintyCode;
	}

	public DSET<ConceptDescriptor> getReasonCode() {
		return reasonCode;
	}

	public void setReasonCode(DSET<ConceptDescriptor> reasonCode) {
		this.reasonCode = reasonCode;
	}

	public ConceptDescriptor getLanguageCode() {
		return languageCode;
	}

	public void setLanguageCode(ConceptDescriptor languageCode) {
		this.languageCode = languageCode;
	}

	public datatypes.r2.foundation.impl.Boolean getIsCriterionInd() {
		return isCriterionInd;
	}

	public void setIsCriterionInd(
			datatypes.r2.foundation.impl.Boolean isCriterionInd) {
		this.isCriterionInd = isCriterionInd;
	}

	public List<ActRelationship> getInboundRelationship() {
		return inboundRelationship;
	}

	public void setInboundRelationship(List<ActRelationship> inboundRelationship) {
		this.inboundRelationship = inboundRelationship;
	}

	public List<ActRelationship> getOutboundRelationship() {
		return outboundRelationship;
	}

	public void setOutboundRelationship(
			List<ActRelationship> outboundRelationship) {
		this.outboundRelationship = outboundRelationship;
	}

	public List<Participation> getParticipation() {
		return participation;
	}

	public void setParticipation(List<Participation> participation) {
		this.participation = participation;
	}

	public static long getSerialversionuid() {
		return serialVersionUID;
	}

}
